build: use github access token for docs site monitoring #24691
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We recently seemed to hit the rate limit in the docs site monitoring job. We can use a Github access token to avoid these rate limit failures. We move the token extraction to a common location where the GCP key is also extracted, and we use a more granular variable name to make sure it's obvious where the key is used (when added to CircleCI)
devversion
added
merge safe
target: patch
andrewseguin
pushed a commit
that referenced
this pull request
Mar 29, 2022
We recently seemed to hit the rate limit in the docs site monitoring job. We can use a Github access token to avoid these rate limit failures. We move the token extraction to a common location where the GCP key is also extracted, and we use a more granular variable name to make sure it's obvious where the key is used (when added to CircleCI) (cherry picked from commit 8a5017d)
forsti0506
pushed a commit
to forsti0506/components
that referenced
this pull request
Apr 3, 2022
We recently seemed to hit the rate limit in the docs site monitoring job. We can use a Github access token to avoid these rate limit failures. We move the token extraction to a common location where the GCP key is also extracted, and we use a more granular variable name to make sure it's obvious where the key is used (when added to CircleCI)
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We recently seemed to hit the rate limit in the docs site monitoring
job. We can use a Github access token to avoid these rate limit failures.
We move the token extraction to a common location where the GCP key is
also extracted, and we use a more granular variable name to make sure it's
obvious where the key is used (when added to CircleCI)